Recently, we had implemented SignaturePointSet and eSignatureAndFieldSupport element changes in PBI's 382028 / 392582. With this continued focus we have implemented the following flags for the eSignatureAndFieldSupport element to return X/Y coordinates:
For more information, see the eSignature feature overview section on the Using eSignature and Acroform fields page.
Previously, users reported slow performance and time out issues when generating documents. These issues occurred with custom organizations where images existed at a parent level.
When a missing image existed: the system scanned the entire organization tree instead of the requested hierarchy level and incrementally scanning the levels above the original level.
This issue has been resolved; we have addressed the issue above through code changes that have replaced the previous method.
In an effort to support returning XY coordinates for all fillable fields we have begun the development work. The first step in supporting this feature is creating a new element (eSignatureAndFieldSupport). This element will only pass XY coordinates for esignatures at this time. In a future release it will control XY coordinates for all fillable fields. See the Using SignaturePointSet and eSignatureAndFieldSupport section in Using eSignature and Acroform fields for details on these two elements.
Recently, Java 8, Saxon, and stylesheet upgrades have been implemented; with these upgrades, users must run a script to remove duplicate imports for the database and file system. Click the link below to access the installation documents and scripts for the appropriate database and file system (.ZIP file).
It was reported that when installing Expere Engine 2015.3.0.1355 on Windows Server 2012 R2, a .NET Runtime Required error appeared stating that .NET 4.0 was required. However, Windows Server 2012 includes .NET 4.5.1.
Users were instructed to either click OK on the error message or create the following folder: C:\Windows\Microsoft.NET\Framework\v4.0.30319, then remove the folder after completing the installation.
This issue has been addressed; we have removed the verification that checks the .NET version. Users can now complete the Expere Engine installation without seeing this error message or performing the workaround above.
When utilizing UseCoverPage with the Ancillary Barcode functionality, data within the Instance Display Name elements would overflow off the cover sheet when too long.
This behavior has been enhanced. The Instance Display Name now wraps on the cover sheet. The following text was added to the cover sheet so recipients of the documents know to return the cover sheet with the document:
When viewing the endpoint URL (Common/WSEndpoint) with NO transaction data, it was expected that Expere would return the results of the GetServiceInfo call; however, the SAXParser threw an exception due to the absence of data. This resulted in the GetServiceInfo call not occurring.
With the Expere 2016.1.3 hotfix, Expere now successfully returns the results of the GetService Info call when the endpoint is viewed with no transaction data.
The ExpereResponse.xml file now contains Cash to Close calculated values available in a new <r:DocCustomDataItems/> parent element and <r:DocCustomDataItem/> child elements. Each of these elements has a DataItemName attribute and number for the value.
The new Expere Engine stylesheet, AddDocCustomDataItem.xsl, adds these elements as DocCustomDataItems.
The new elements exist as children and grandchildren of the <r:DocDescriptor/> element. The <r:DocCustomDataItem/> elements contain the following DataItemName attribute values:
The following code snippet appears in the ExpereResponse.xml file:
<r:DocDescriptor> <r:DocID>PKGD.LoanEstimate</r:DocID> <r:DocType>Dynamic</r:DocType> <r:DocDisplayName>Loan Estimate</r:DocDisplayName> <r:DocRootEntityName>INS.LoanEstimate</r:DocRootEntityName> <r:DocCustomDataItems> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateTotalClosingCostsStoredValueAmount">34287</r:DocCustomDataItem> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateClosingCostsFinancedStoredValueAmount">-34287</r:DocCustomDataItem> <r:DocCustomDataItem DataItemName="/Txn/IntegratedDisclosuresLoanEstimateCashToCloseStoredValueAmount">107815</r:DocCustomDataItem> </r:DocCustomDataItems> </r:DocDescriptor>
Previously, hosted and non-hosted transactions that called the Expere Engine failed when using certain special characters on static documents.
We have enhanced the Expere Engine to support the following special characters:
Newly Supported:
Existing (Previously Supported):
We have laid the ground work for a future enhancement to support additional hosted platforms. However, no customer-facing changes currently exist for this change. We will provide additional information as it impacts our users in a future release.
Logging has been enhanced for the caching and file system repository to help track the progress of requests; these enhancements include the RequestID, OrgID, and PackageID. This enhancement is also a result of the changes made in PBI 382041 below.
Changes were made to the file system repository to make the indexing process more efficient.
Previously, users could not enable or disable eSignatures or AcroForm fields for transactions.
Users can now pass eSignature and Acroform values in the AncillaryOutput of a SelectAndGenerate or Generate request. For detailed information on enabling or disabling eSignature or Acroforms, see Using eSignature and Acroform fields.
Previously, an issue existed in the Expere Config Tool utility (Important update regarding the Expere Config Tool) in the 2016.1 release. Users reported an error when launching the Expere Config Tool utility and as a result, could not update various fields.
As a workaround, we had provided instructions on how to manually update the following configuration files and various settings within these files:
The Expere Config Tool has been enhanced, consisting of the following:
Users can access the updated Expere Config Tool utility here.
An issue had been identified with certain PDF viewers and e-signatures. Specifically, documents with e-signatures turned on but not captured, would display, and sometimes print a box around the signature field.
This has been corrected; e-signature capable documents, where an e-signature has not been captured, will no longer display or print a box around the signature field.
Previously, when a document was removed from base content, OPPSA stopped printing when it encountered the missing document. In some instances, the system stopped printing any remaining documents depending on where the document was located.
This behavior has been enhanced; when an OPPSA package includes a document that has been removed, an error appears stating which document must be removed from the specified package in the OPPSA product.
Summary: Embedded versions of Expere .NET and Requirements Editor now utilize Java 8 and Saxon.
For more information, see the following Expere System Requirements Sections:
We have recently consolidated the .NET and Java installation procedures to now reside in one webhelp implementation, available here: Expere Implementation Guide.
Issue: Previously, the Expere Engine reserved space for ancillary barcodes on dynamic documents even though the barcode element was not included in the .REQ file.
Solution: This issue has been resolved; when generating a dynamic document and selecting an ancillary barcode option, the document will no longer reserve space for the barcode if the .REQ file does not contain a barcode element.
This feature requires an Expere Engine update.